In 2010, every payments company sold to the same person: the CFO. Finance teams signed the contracts, ran procurement, and picked a vendor off a spreadsheet of bids.
But Stripe aimed somewhere stranger. They built the entire company around the developer, the person actually pasting code into a website at 2am.
This one choice shaped everything that followed. It turned seven lines of code into a company valued at $159 billion, moving $1.9 trillion in payments a year, roughly 1.6% of global GDP.
Here is how winning the developer became the whole growth engine.
Why payments stayed broken for so long
Accepting money online used to be a slog. You applied for a merchant account, waited weeks for bank underwriting, stitched together a gateway, passed a PCI compliance audit, and hoped your code talked to the bank correctly.
Every builder knew this pain. Thousands of engineers felt it daily. So why did nobody fix it?
Paul Graham, the English-American computer scientist and entrepreneur, named the answer "schlep blindness." A schlep is a tedious, unpleasant task, and our brains quietly refuse to even see business ideas built around one. Founders kept launching recipe sites while the most valuable plumbing of the internet sat broken in plain view.
Patrick and John Collison, two brothers from an Irish village of about 200 people, had already sold one startup as teenagers. They kept hitting the payments wall on every new project. So they asked a sharper question: what would turn payments into something as simple as adding a software library to your code?
The answer became seven lines of code you could paste in and start charging customers that same afternoon.
Doing the unscalable things on purpose
Early Stripe was barely a company. When someone signed up, Patrick would call a friend who manually set up a merchant account on the back end. That is a Wizard of Oz MVP: a manual process dressed up to look finished, used to test real demand before building the machinery. Uber ran the same play, texting people their driver details by hand.
The brothers paired that with a tactic, now called the "Collison installation." Most founders, when a prospect said yes, replied, "Great, we'll send you a link." The Collisons said, "Give me your laptop," and set it up right there. They refused to let interest fade into inaction.
A clever pricing move sat underneath all of this. During beta, Stripe charged at the expensive end, around 5% plus 50 cents when rivals sat near 2.9%. Premium pricing filtered out bargain hunters and pulled in people who genuinely needed the product to work. Customers paying double also tell you fast when something is not twice as good.
The docs were the marketing
Stripe barely ran ads. For roughly the first year, their only paid channel was Stack Overflow, the forum where developers already hung out.
Their real growth lever was the product experience, especially the documentation. Stripe treated docs as a core part of the product, with clean examples a developer could copy, run, and ship in minutes. One early customer reportedly said the API docs read like poetry.
When you make a painful task feel effortless, developers talk. They posted on Hacker News, recommended it in Slack groups, and pushed for it at work. Payments software has no business going viral, yet Stripe spread by word of mouth because everything else felt so bad to use.
That created a bottom-up adoption loop. A developer tries Stripe on a side project, loves it, and by the time finance gets involved, the integration is already live.
The compounding nobody saw coming
Selling to startups looked like the small-money option. Tiny companies, tiny volumes. Stripe was playing a longer game.
Startups grow up. Young engineers become decision-makers. Many companies that picked Stripe in a YC batch became Shopify, Lyft, and Instacart, and Stripe grew with every dollar they processed. A startup that helps other people make money tends to make money itself.
The headcount reflects the strategy. Around 2021, roughly 3% of Stripe worked in sales, while competitor Checkout.com had close to 13% in sales roles. Stripe let the product sell itself at the bottom of the market, then added a sales team for enterprise once the brand was already trusted inside those companies.
It developed into a moat. Once a business builds its billing, checkout, and reporting on your APIs, ripping it out is a months-long engineering project. Adding Connect, Radar, and Atlas on top makes switching to save a fraction of a percent no longer sensible.
What you can borrow from this
1. Pick the user, not the buyer.
Stripe serves the person who installs the product, not the one who signs the check. Figure out who actually touches your tool every day, then build the whole experience around making their life easier.
2. Make your hardest onboarding step embarrassingly easy.
Seven lines of code beat seven weeks of paperwork. Find the one moment where new users get stuck and shrink it from days to minutes.
3. Treat docs, onboarding, and support as growth channels.
A product that delights its first users turns them into your sales team. Word of mouth inside a tight community will outrun any ad budget you could buy.
4. Use price as a filter in the early days.
Charging more can attract the right customers and pressure you to build something genuinely worth it. Cheap pricing often invites the wrong crowd.
5. Start where the market is small but compounding.
Win the customers who will grow into giants, then grow alongside them as they expand.
Stripe won by picking one specific human, the developer, and making that person's worst task feel like magic. Everyone who tried it became a reason for the next person to try it.
This is what a bottom-up growth loop does quietly. Choose your target audience, eliminate their biggest pain point, and let them spread the word for you.
Found this useful? Forward it to a founder or builder who needs it.
